Integrating a mobile hotspot into a larger network environment

ABSTRACT

Integration of a mobile hotspot into a service provider network is disclosed. A network node establishes a first wireless communication link with a mobile hotspot device. The mobile hotspot device is configured to establish a second wireless communications link with at least one client device. The network node receives an access request message from the mobile hotspot device which comprises credentials provided by the at least one client device. The network node determines that the at least one client device is authorized to access the service provider network through the mobile hotspot device based on the credentials and indicates to the mobile hotspot device that the at least one client device is authorized to access the service provider network through the mobile hotspot device.

RELATED APPLICATIONS

This application claims the benefit of provisional patent application Ser. No. 61/599,081, filed Feb. 15, 2012, the disclosure of which is hereby incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to wireless access of a network, and in particular to the integration of a mobile hotspot device into a larger network environment.

BACKGROUND

New “4G” cellular data technologies such as WiMax and LTE make high-bandwidth applications, such as streaming video applications, possible. Such applications have driven the demand for data by consumers. Wireless service providers are making significant investments in their infrastructure to meet this demand. Because wireless subscription fees are extremely competitive, service differentiators are increasingly important to maintain existing subscribers and attract new ones. Moreover, data usage instead of voice communications is driving revenue for service providers, so service providers are incented to find ways to increase demand for data by its subscribers.

Many mobile devices today include a wireless interface such as a Wi-Fi interface that allows the mobile device to connect to a wireless local area network and access the Internet. Some of these mobile devices, such as cellular phone mobile devices, also include a cellular interface that allows the mobile device to access the Internet via a cellular communication link even when not in the presence of a wireless local area network, such as when in a vehicle. Such devices increasingly also have hotspot functionality that allows the mobile device to serve as a mobile hotspot, such that other Wi-Fi capable devices, referred to herein as client devices, may connect to the mobile device via the Wi-Fi interface, and access the Internet via the mobile device's cellular communication link. In this role the mobile device serves essentially as a wireless access point and router for client devices that would not otherwise have access to the Internet.

A service provider creates a potential new portal to their network each time one of their subscribers' devices with hotspot functionality is within wireless range of the service provider network. Since cellular phones increasingly have such functionality, it would be beneficial if a service provider could leverage its subscribers' devices to offer Internet access (and facilitate corresponding data usage) to other devices that are in Wi-Fi proximity of the cellular device, in a manner that benefits the service provider, as well as its subscribers.

SUMMARY

The present disclosure discloses mechanisms for facilitating access to a service provider network by integrating mobile subscriber devices into the service provider network, and thereby extending the reach of the service provider network to any location that a subscriber's device is enabled. In one embodiment, the subscriber's device, sometimes referred to herein as a mobile hotspot device (MHD), may be configured, or provisioned, automatically by the service provider with a wireless local area network (LAN) having a predetermined name, such as a predetermined service set identifier (SSID). The MHD may periodically broadcast the SSID to any other devices, sometimes referred to herein as client devices, which may be in wireless range of the MHD. Certain client devices may be programmed to detect the predetermined SSID, and in response, attempt to establish communication with the service provider network via the MHD.

In one embodiment, the client device may communicate credentials to the MHD. The MHD generates an access request message that includes the credentials, and sends the access request message to the service provider network for authentication. A network node in the service provider network receives the access request message, determines that the client device is authorized to access the service provider network through the MHD based on the credentials, and indicates to the MHD that the client device is so authorized.

In one embodiment, authorization may in part be based on whether a user of the client device has a subscription to access the service provider network. For example, the client device may comprise a cellular phone that receives service via the service provider network in accordance with the subscription with the service provider. The client device may have Wi-Fi capability, but not cellular data capability. The client device may include a client application that detects broadcasted SSIDs, and upon detecting an SSID that is the predetermined SSID, such as the hotspot offered by the MHD, recognize the hotspot as a service provider wireless LAN, and initiate the authorization sequence mentioned above automatically. Once authorized, the user of the client device enjoys Internet access that may not otherwise be obtainable at that particular location. In another embodiment, the client device may comprise a Wi-Fi capable laptop computer or tablet computer of a subscriber of the service provider. The client device includes the client application as well as suitable credentials that identify the device as being associated with the subscriber.

In one embodiment, the MHD is a cellular phone that enjoys access to the service provider network by virtue of a subscription between an owner of the MHD and the service provider. The MHD may concurrently provide both voice service to the owner, as well as mobile hotspot functionality such as data communications between the Internet and one or more client devices. Data usage by each client device may be counted against the subscription associated with the respective client device, rather than the MHD, so that the owner of the MHD is not penalized for providing access to the service provider network. Data usage by client devices that are associated with the subscription of the MHD, such as family members' client devices, may be counted against the subscription of the MHD. In one embodiment, the network node may determine that a client device has exceeded an allotment, such as a monthly allotment, associated with the client device subscription, and de-authorize access by the client device to the service provider network.

Prioritization of requests for data may be based on the client device to which the data is destined. In particular, data requested by the MHD may enjoy a higher priority than data requested by a client device. In this manner, the owner of the MHD is not penalized for allowing the MHD to be used as a mobile hotspot. For example, if the owner of the MHD initiates a first request for a first streaming movie from an Internet movie service, and a user of a client device similarly initiates a second request for a second streaming movie from an Internet movie service, sufficient bandwidth may be reserved for the first streaming movie so that the first streaming movie is provided at a relatively high resolution. Remaining bandwidth may be insufficient to provide the second streaming movie, or may require that a lower resolution version be provided to the client device. Such prioritization mechanisms may be implemented by the network node, the MHD, or a combination of both.

In one embodiment, upon receipt of a connection request by a client device, the MHD may access configuration data maintained on the MHD that identifies permitted client devices. For example, the owner of the MHD may identify family members' and particular associates', friends' or colleagues' client devices as being permitted client devices. If the client device is not identified in the configuration data as a permitted client device, the MHD does not generate and send an access request message with the client device's credentials to the network node, effectively barring access to the service provider network by the client device.

In one embodiment, the owner of the MHD may be compensated by the service provider for allowing the MHD to be used as a portal to the service provider network. For example, the service provider may reduce a portion of the monthly subscription fee of the owner based on the quantity of data that travels through the MHD on a path to a client device. Alternatively or additionally, the service provider may increase a data usage allotment associated with the MHD such that the MHD enjoys a larger data usage allotment based on the quantity of data that travels through the MHD on a path to a client device. Those of skill in the art will recognize that other compensation mechanisms are possible.

Those skilled in the art will appreciate the scope of the present disclosure and realize additional aspects thereof after reading the following detailed description of the preferred embodiments in association with the accompanying drawing figures.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

FIG. 1 is a block diagram illustrating a system in which embodiments of the present disclosure may be practiced;

FIG. 2 is a block diagram of the system illustrated in FIG. 1 showing greater detail of certain components;

FIG. 3 illustrates an exemplary message flow for facilitating access to a service provider network by a client device via a mobile hotspot device (MHD);

FIG. 4 is a block diagram of the system illustrated in FIG. 1 according to another embodiment;

FIG. 5 illustrates an exemplary message flow for providing voice signals and data destined for different devices to the MHD concurrently;

FIG. 6 illustrates an exemplary message flow for accounting for data usage by devices that receive data via the service provider network according to one embodiment;

FIG. 7 illustrates another exemplary message flow for accounting for data usage by devices that receive data via the service provider network according to another embodiment;

FIG. 8 illustrates an exemplary message flow for prioritizing data provided to one device over data provided to another device according to one embodiment;

FIG. 9 is a block diagram of an exemplary network node according to one embodiment; and

FIG. 10 is a block diagram of an exemplary MHD according to one embodiment.

DETAILED DESCRIPTION

The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.

The present disclosure discloses mechanisms for facilitating access to a service provider network by integrating mobile subscriber devices into the service provider network, and thereby extending the reach of the service provider network to any location that a subscriber's device is enabled. In one embodiment, the subscriber's device, sometimes referred to herein as a mobile hotspot device (MHD), may be configured, or provisioned, automatically by the service provider with a wireless local area network (WLAN) having a predetermined name, such as a predetermined service set identifier (SSID). In one embodiment, the MHD periodically broadcasts the SSID to any other devices, sometimes referred to herein as client devices, which may be in wireless range of the MHD. Certain client devices may be programmed to detect the predetermined SSID, and in response, attempt to establish communication with the service provider network via the MHD.

In another embodiment, rather than have an MHD broadcast its SSID, a client device may be preconfigured with the SSIDs of one or more MHDs, and may periodically check to determine if it is within range of such an MHD by attempting to connect to such preconfigured SSIDs.

FIG. 1 is a block diagram illustrating a system 10 in which embodiments of the present disclosure may be practiced. The system 10 includes a service provider network 12 that includes a cellular network 14 and one or more network nodes 16. The service provider network 12 is associated with a particular service provider, such as a wireless service provider or the like. The cellular network 14 comprises equipment associated with providing cellular voice and data access to subscriber devices, such as cellular phones, and may comprise, for example, antennas, base stations, base station controllers and the like. The service provider network 12 includes one or more network nodes 16 that comprise computing or processing devices, which, among other functionality that will be discussed in greater detail herein, couples the service provider network 12 with other networks, such as the Internet 18. While for purposes of illustration, the network node 16 is depicted as being separate from the cellular network 14, the network node 16 may be a part of the cellular network 14. Preferably, but not necessarily, the cellular network 14 implements 4G or greater bandwidth through a technology such as WiMax or LTE.

The service provider network 12 may also include one or more WLANs 20 placed at locations such as airports, coffee shops, shopping malls, and the like, which offer access via the service provider network 12 to the Internet 18 to subscribers or transient users.

A mobile hotspot device (MHD) 22 includes a wireless cellular interface 24 that establishes a wireless communications link 26 with the cellular network 14. The wireless cellular interface 24 may comprise any suitable circuitry and/or software necessary to facilitate the establishment of the wireless communications link 26. The wireless communications link 26 is established in accordance with the conventional signaling and connection mechanisms associated with the cellular network 14. The MHD 22 comprises any portable, mobile computing or processing device capable of establishing the wireless communications link 26, such as a smart phone like an Apple® iPhone®, an Android®-based phone, or the like, a laptop computer that includes cellular data interface circuitry, a computer tablet like the Apple® iPad®, Samsung Galaxy®, or the like, or a special purpose hotspot device, such as the Sprint® Overdrive® or the like.

The MHD 22 also includes a WLAN interface 28 suitable for establishing one or more wireless WLAN communication links, such as Wi-Fi™ communication links. The MHD 22 may also have one or more other wireless interfaces 30, such as a ZigBee wireless interface, a Bluetooth® wireless interface, and the like. A wireless router module 32 implements a hotspot capability in the MHD 22. The wireless router module 32 establishes a hotspot 34 via the WLAN interface 28 (or via the other wireless interface 30) such that one or more client devices 36-1-36-N (generally, client devices 36) within the hotspot 34 may connect to the MHD 22 via corresponding wireless communication links 38-1-38-N (generally, wireless communication links 38). The precise boundaries of the hotspot 34 may vary based on any number of factors, including obstructions, the particular wireless technology used, i.e., Wi-Fi, ZigBee, Bluetooth®, etc., interference from other RF emitters, and the like. The wireless router module 32, as described in greater detail herein, routes requests for data from a client device 36 to the network node 16, and routes data from the network node 16 that is destined for client devices 36 to the appropriate client devices 36.

The client devices 36 comprise any computing or processing device that includes a wireless interface capable of establishing a wireless communication link 38 with the MHD 22. For example, the client device 36-1 may comprise a smart phone, such as an Apple® iPhone®, an Android®-based phone, or the like. The client device 36-2 may comprise a laptop computer. The client device 36-N may comprise a computer tablet like the Apple® iPad®, Samsung® Galaxy®, or the like.

In one embodiment, the MHD 22 implements the hotspot 34 via a WLAN having a predetermined service set identifier (SSID) that is associated with the service provider network 12. The MHD periodically beacons, or otherwise broadcasts, the SSID within the hotspot 34. A client device 36, such as the client device 36-1, receives the beacon, and may be programmed or otherwise configured to recognize the predetermined SSID. The client device 36-1 then attempts to connect to the MHD 22 by establishing a respective wireless communications link 38 with the MHD 22. After establishing a wireless communications link 38 with the MHD 22, the client device 36-1 may automatically provide the MHD 22 credentials that identify the client device 36-1. The MHD 22 generates an access request message that includes the credentials and communicates the credentials via the cellular network 14 to the network node 16. The network node 16 receives the access request message and authenticates the client device 36-1 as being authorized to access the service provider network 12 based on the credentials. The network node 16 indicates to the MHD 22 that the client device 36-1 is authorized to access the service provider network 12. Thereafter, with respect to the client device 36-1, the MHD 22 serves primarily as a wireless router that facilitates communications between the client device 36-1 and the service provider network 12. Via the service provider network 12, the client device 36-1 may access other networks, such as a private network or the Internet 18. Note that in one embodiment the exchange of communications between the client device 36-1, the MHD 22, and the network node 16 happens automatically upon the client device 36-1 detecting the predetermined SSID. This eliminates the need for a user 42-1 to enter usercodes, passwords, and the like. Merely by moving the client device 36-1 within the hotspot 34 the user 42-1 may thereby obtain authenticated access to the Internet 18.

Providing such access to the client device 36-1 may be beneficial to the service provider, an owner 40 of the MHD 22, and the users 42-1-42-N (generally users 42) of the client devices 36. In one embodiment, authorization to access the service provider network 12 may be based, at least in part, on whether a user 42 has a subscription with the service provider. Data consumed by a client device 36 may be counted against a data usage amount associated with the subscription of the respective user 42. This benefits the service provider because it facilitates selling more data to the respective user 42. The ability to access the Internet 18 by the user 42 from locations where the user 42 may not otherwise be able to access the Internet 18 benefits the user 42. The owner 40 of the MHD 22 may also be compensated by the service provider in terms of an increased data usage amount associated with the subscription of the owner 40, a reduced subscription fee, or in other ways.

FIG. 2 is a block diagram of the system 10 illustrated in FIG. 1 showing greater details of some of the components. The network node 16 may include a remote configuration module 44 that interfaces with a configuration module 46 in the MHD 22 to configure the MHD 22 to have a wireless LAN with a predetermined SSID. Such configuration of the MHD 22 may be automatically initiated, for example, after the owner 40 indicates to the service provider that the owner 40 agrees to permit the MHD 22 to serve as a portal via which the client devices 36 can access the service provider network 12. This agreement may be indicated, for example, by accepting the terms of a contract presented on the website of the service provider. The contract may include terms and provisions whereby in return for allowing the MHD 22 to serve as a portal, the owner 40 will be compensated in one or more of the ways discussed above. Such acceptance may trigger the network node 16 to automatically configure the MHD 22 with the predetermined SSID. Such acceptance may also trigger additional software to be loaded onto the MHD 22 by the network node 16 to implement the hotspot functionality, provide desired accounting or prioritization functionality for data destined to the MHD 22 or the client devices 36, or any other desired or appropriate processing to carry out the functionality described herein.

In another embodiment, the owner 40 may configure the MHD 22 to have the wireless LAN with the predetermined SSID based on configuration instructions provided by the service provider during the process of accepting the contract. In one embodiment, the service provider may remotely manage the wireless LAN with the predetermined SSID in the MHD 22, including, for example, managing an encryption type, traffic policing, rate shaping, implementing a quality of service (QOS) policy, remote monitoring, and the like. Remote management may include limiting the number of connections of client devices 36 to the MHD 22. Such remote management may be implemented by any suitable means, including, for example, one or more of SNMP, OMA-DM, TR69, XML, and the like. The network node may also implement a user interface for a service provider operator to remotely manage the MHD 22.

In one embodiment, the network node 16 also includes an authentication module 48 used to authenticate the client device 36 in response to an access request message received from the MHD 22. Such authentication module 48 may access information, such as configuration data 50, to determine whether the credentials included in the access request message identify a known user 42. A rate limiting, policing and prioritization module 52 may, in accordance with rules or criteria identified in the configuration data 50 or received from the MHD 22, limit the rate of certain data flows to the MHD 22 and/or prioritize such data flows. For example, one user 42 may, based on a particular subscription, enjoy a 3 mega-bit per second (mbps) data rate, and another a 1 mbps data rate. Alternately, after a user 42 exceeds the data usage allotment, or threshold, associated with their subscription, additional data may be provided at an increased cost, and/or at a reduced data rate. The MHD 22 may also be able to identify certain client devices 36, such as family members' client devices 36, as having a higher priority, or faster data rates, than any other client devices 36. In another embodiment, the MHD 22 may implement the rate, policing and prioritization function discussed herein in a rate limiting, policing and prioritization module 54 contained in the MHD 22.

A billing module 56 in the network node 16 may, among other features, maintain data usage by various client devices 36 and the MHD 22, and cut-off, or de-authorize, client devices 36 that exceed predetermined data usage allotments associated with respective subscriptions, or ensure that data used in excess of such predetermined data usage allotments are charged at higher incremental rates. The billing module 56 may also allocate certain data usage by client devices 36 to the MHD 22, such as those client devices 36 that are associated with the same subscription as the MHD 22. The billing module 56 may also maintain information suitable for compensating the owner 40 for allowing the MHD 22 to be used as a portal to the service provider network 12.

The wireless router module 32 may maintain data that identifies one or more wireless local area networks that are implemented by the MHD 22. For example, network configuration data 58 may identify a personal Wi-Fi network that has a private SSID that the owner 40 provides to only close friends and family members. Network configuration data 60 may define the Wi-Fi network automatically configured by the remote configuration module 44 that offers a portal to the service provider network 12 for any client devices 36 that detect and identify the predetermined SSID. The network configuration data 60 may be configured with any suitable parameters or attributes associated with a wireless LAN.

SSIDs may also be used by the rate limiting, policing and prioritization module 52 or the rate limiting, policing and prioritization module 54 as the basis for rate limiting and/or prioritization. For example, devices communicatively coupled to the MHD 22 via the private SSID may enjoy higher data rates and/or priority than those communicatively coupled to the predetermined SSID.

In one embodiment, the MHD 22 may also contain configuration data 62 that includes, among other information, a permitted client devices list 64. The permitted client devices list 64 may identify client devices 36 that are permitted by the MHD 22 to access the service provider network 12. Thus, upon receiving a request from a client device 36 to connect to the MHD 22, the MHD 22 may first verify that the client device 36 is identified on the permitted client devices list 64, and if not, refuse to allow the client device 36 to connect to the MHD 22.

The client devices 36 may contain a client application 66 provided by the service provider network 12 that is programmed to detect and identify the predetermined SSID beaconed or otherwise broadcast by an MHD, such as the MHD 22. The predetermined SSID may not be identical across each MHD 22, and the phrase “predetermined SSID” encompasses any naming convention that would permit a client device 36 to detect and identify the SSID as potentially being associated with the service provider. For example, a first portion of the SSID may be generic across all MHDs 22, and a second portion of the SSID may be unique to a particular MHD 22. The client application 66 may parse each available SSID and upon determining that an SSID contains the first generic portion associated with the service provider network 12, attempt to connect to the service provider network 12. The client application 66 may be downloaded from a website offered by the service provider, or may be a part of the initial software package provided on the client device 36 when purchased from the service provider. In another embodiment, the client device 36 may be preconfigured with the SSID of the MHD 22, and may periodically check to determine if it is within range of the MHD 22 by attempting to connect to the MHD 22 via such preconfigured SSID.

FIG. 3 illustrates an exemplary message flow for facilitating access to the service provider network 12 by a client device 36 via the MHD 22. FIG. 3 will be discussed in conjunction with FIG. 2. Initially, assume that the network node 16 initiates a configuration sequence with the MHD 22 to generate a wireless local area network having a predetermined SSID (FIG. 3, step 1000). The MHD 22 generates the network and acknowledges this to the network node 16 (FIG. 3, steps 1002-1004). The MHD 22 enables the network and thereby offers the hotspot 34 (FIG. 3, step 1006).

The client device 36-1 receives the beacon identifying the hotspot with the predetermined SSID. The client device 36-1 identifies the hotspot as having the predetermined SSID (FIG. 3, step 1008). Because the client device 36-1 recognizes the hotspot 34 as one associated with the service provider network 12, the client device 36-1 establishes a wireless communication link 38-1 with the MHD 22, and provides the MHD 22 credentials for authentication with the service provider network 12 (FIG. 3, step 1010). If the MHD 22 maintains a permitted client devices list 64, the MHD 22 accesses the permitted client devices list 64 to determine whether the client device 36-1 is identified as a permitted device (FIG. 3, step 1012). The MHD 22 then generates and sends an access request message that includes the credentials provided by the client device 36-1 to the network node 16 (FIG. 3, step 1014). The network node 16 determines that the client device 36-1 is authorized to access the service provider network 12 based on the credentials (FIG. 3, step 1016). The network node 16 indicates to the MHD 22 that the client device 36-1 is authenticated, and therefore authorized to access the service provider network 12 through the MHD 22 (FIG. 3, step 1018). The MHD 22 notifies the client device 36-1 that the client device 36-1 is authorized to access the service provider network 12 (FIG. 3, step 1020).

In one embodiment, at some point during the authentication process, the network node 16 may communicate a message to the MHD 22 indicating that the client device 36-1 seeks to access the service provider network 12 through the MHD 22. The MHD 22 may present this to the owner 40, along with options, such as Allow or Reject. If the owner 40 selects the Reject option, the MHD 22 informs the network node 16 that the request has been denied and the network node 16 rejects the access request message. If the owner 40 selects the Allow selection, the network node 16 indicates to the MHD 22 that the client device 36-1 is now permitted to access the service provider network 12. In another embodiment, prior to even sending the access request message to the network node 16, the MHD 22 may identify the client device 36-1 and provide the owner 40 an Allow or Reject option upon receiving the credentials from the client device 36-1

FIG. 4 is a block diagram of the system illustrated in FIG. 1 according to another embodiment. In this embodiment the MHD 22 detects the presence of the WLAN network 20. The owner 40 or the MHD 22 determines that the WLAN network 20 is associated with the service provider network 12 and that the service provider network 12 is therefore accessible. The MHD 22 establishes a wireless communications link 68 with the WLAN network 20, and communicates with the network node 16 as discussed previously, except through the WLAN network 20 instead of the cellular network 14. Whether the MHD 22 is connected via the WLAN network 20 or the cellular network 14 may be transparent to any client devices 36 that connect to the service provider network 12 via the MHD 22. The MHD 22 may select the WLAN network 20 over the cellular network 14 based on certain criteria, such as a bandwidth of the WLAN network 20 compared to that of the cellular network 14, or may select the WLAN network 20 because of financial criteria, such as the service provider may not charge the MHD 22 for data usage via the WLAN network 20, or may charge at a reduced rate with respect to the cellular network 14.

FIG. 5 illustrates an exemplary message flow for providing voice signals and data destined for different devices to the MHD 22 concurrently. Assume that the service provider network 12 has authenticated the client device 36-1 to access the service provider network 12 via the MHD 22. Assume further that the MHD 22 is coupled to the service provider network 12 via the wireless communications link 26 with the cellular network 14. The owner of the MHD 22 is participating in a voice call with another party. Concurrently with the voice call, the client device 36-1 seeks data such as a web page or video from the Internet 18. The network node 16 thus concurrently provides voice signals from the other party to whom the owner 40 is speaking and data destined for the client device 36-1 to the MHD 22 (FIG. 5, step 2000). The MHD 22 renders the voice signals to the owner 40, such as via a speaker contained in the MHD 22 (FIG. 5, step 2002). The MHD 22 also substantially concurrently provides the data that is destined for the client device 36-1 to the client device 36-1. Thus, in the case where the MHD 22 comprises a smart phone, for example, the owner 40 may enjoy cellular voice capabilities while the MHD 22 concurrently serves as a portal to the service provider network 12 for the client device 36-1.

FIG. 6 illustrates an exemplary message flow for accounting for data usage by devices that receive data via the service provider network 12 according to one embodiment. In this embodiment the owner 40 uses the MHD 22 to access the Internet 18 at substantially the same time the user 42-1 uses the client device 36-1 to access the Internet 18. The MHD 22 generates a request for data X and sends the request to the network node 16 for communication to the Internet 18 (FIG. 6, step 3000). The client device 36-1 substantially concurrently generates a request for data Y and sends the request via the MHD 22 to the network node 16 for communication to the Internet 18 (FIG. 6, steps 3002-3004). The network node 16 receives the requested data from the Internet 18 and provides data X and Y to the MHD 22 (FIG. 6, step 3006). The MHD 22 consumes data X, i.e., presents data X to the owner 40 or otherwise processes data X in accordance with the purposes of requesting data X, and provides data Y, which is destined for the client device 36-1, to the client device 36-1 (FIG. 6, steps 3008-3010).

The network node 16 maintains data usage quantifiers, such as counters, for both the MHD 22 and the client device 36-1 in order to monitor their cumulative data usage in accordance with their respective subscriptions with the service provider. Thus, the network node 16 increases the data usage quantifier of the MHD 22 by the amount of data X (FIG. 6, step 3012). The network node 16 also increases the data usage quantifier of the client device 36-1 by the amount of data Y (FIG. 6, step 3014). The network node 16 determines that the data usage quantifier associated with the client device 36-1 now exceeds the monthly allotment for the client device 36-1 based on the subscription via which the client device 36-1 obtains access to the service provider network 12 (FIG. 6, step 3016). The network node 16 sends a message to the MHD 22 de-authorizing access to the service provider network 12 by the client device 36-1 (FIG. 6, step 3018). The MHD 22 disconnects the client device 36-1 to prevent further access to the service provider network 12 (FIG. 6, step 3020). The MHD 22 may also provide information to the client device 36-1 for display to the user 42-1 explaining the reason the client device 36-1 has been disconnected.

It will be apparent that de-authorizing the client device 36-1 is only one of several different actions that network node 16 may take upon determining that the data usage quantifier associated with the client device 36-1 exceeds the monthly allotment. For example, the network node 16 may simply continue to allow the client device 36-1 to access the service provider network 12 even though the data usage exceeds the monthly allotment because the user 42-1 may be charged for such data at a higher rate than for data under the monthly allotment. The network node 16 may also prioritize data differently based on whether the client device 36 for which the data is destined has exceeded the monthly data usage allotment. In particular, the network node 16 may prioritize data requests from such client devices 36 at a lower priority than data requests from client devices 36 that have not exceeded their monthly data allotments.

In another embodiment, the MHD 22 may track data usage of client devices 36, and provide various actions based on the data usage quantifier associated with a client device 36. For example, if the MHD 22 determines that a particular client device 36 is accessing a significantly higher quantity of data than other client devices 36, the MHD 22 may prioritize other client devices 36 over such client device 36. The MHD 22 may also receive, from the network node 16, the data usage quantifiers associated with the client devices 36, tally the data consumed by the client devices 36, and disconnect or otherwise de-authorize client devices 36 that have exceeded a monthly allotment associated with the respective subscription. Upon disconnect of a client device 36, either voluntarily or involuntarily, the MHD 22 may provide the updated data usage quantifier to the network node 16 for billing and accounting purposes.

FIG. 7 illustrates another exemplary message flow for accounting for data usage by devices that receive data via the service provider network 12 according to another embodiment. In this embodiment the client device 36-2 is associated with the subscription of the MHD 22. For example, the client device 36-2 may be identified in the subscription as one of several client devices 36 that are permitted to access the service provider network 12 pursuant to the subscription. The client device 36-2 generates a request for data X and sends the request via the MHD 22 to the network node 16 for communication to the Internet 18 (FIG. 7, steps 4000-4002). The network node 16 receives data X from the Internet 18 and determines that the client device 36-2 is associated with the subscription of the MHD 22 (FIG. 7, step 4004). The network node 16 then adjusts the data usage quantifier associated with the MHD 22 by the quantity of data X (FIG. 7, step 4006). The network node provides data X to the MHD 22 for communication to the client device 36-2 (FIG. 7, steps 4008-4010).

FIG. 8 illustrates an exemplary message flow for prioritizing data destined for one device over data destined for another device according to one embodiment. Assume that the owner 40 requests data X, which comprises a first movie stream, from the Internet 18. The network node 16 receives the request from the MHD 22 for data X, and begins providing the first movie stream to the MHD 22 for presentation to the owner 40 (FIG. 8, steps 5000-5002). The user 42-1, while the movie is being streamed to the MHD 22, then requests data Y, which comprises a second movie stream. The client device 36-1 generates a request for data Y and sends it to the network node 16 via the MHD 22 (FIG. 8, steps 5004-5006). The network node 16 receives the request for data Y, and recognizes that data X is destined for the MHD 22, while data Y is destined for the client device 36-1, which is a device other than the MHD 22. The network node 16 prioritizes the data X stream over the data Y stream (FIG. 8, step 5008). Such prioritization can take any of several different forms. In the case of streams of data, such as a movie stream, the network node 16 may allocate a larger bandwidth to the MHD 22 than to the client device 36-1. The reduced bandwidth available to the client device 36-1 may result in a lower resolution movie being provided to the client device 36-1, or may cause less fluid playback of the movie than that enjoyed by the owner 40. The network node 16 then provides the data X and Y to the MHD 22 and client device 36-1, respectively, in accordance with the priority (FIG. 8, steps 5010-5012).

Prioritization may be configured by the owner 40 such that certain client devices 36, such as those associated with the subscription via which the MHD 22 accesses the service provider network 12, have higher priority than any other client devices 36. The owner 40 may indicate that the MHD 22 enjoys a highest priority in any situation. Alternatively, prioritization may be determined by the service provider and may be based on subscription level, subscription status, type of data being requested, or any other criteria.

In one embodiment, the MHD 22 may be able to provide location services for a client device 36 that cannot otherwise provide a location. For example, the MHD 22 may include a GPS receiver that allows the MHD 22 to identify its current location on the earth. If the MHD 22 is connected to a client device 36 via a wireless communication link 38, then the client device 36 is likely within several hundred feet of the MHD 22. If the wireless communication link 38 comprises a Bluetooth® or ZigBee wireless communications link 38, then the client device is likely even closer to the MHD 22. If requested, the MHD 22 may be able to report its own location as the location of the client device 36 and while not exact, may suffice for an emergency situation.

In one embodiment, one MHD 22 may initiate a handoff of a client device 36 to another MHD 22, or to a cellular base station, picocell, femtocell, or the like based on, for example, metrics related to signal performance (e.g., signal strength, throughput capability, latency, congestion), cost (e.g., cost of building and maintaining capacity on the network to which the client device 36 would be transferred), user input (e.g., the owner 40 of the MHD 22 may select to have the client device 36 transfer to another network, or the user 42 of the client device 36 may select to be transferred to another network based on pre-set or dynamically chosen selection criteria), battery life remaining on the MHD 22, or location of the MHD 22 or the client device 36, for example. The handoff may be initiated by the MHD 22 or by the client device 36.

FIG. 9 is a block diagram of a network node 16 according to one embodiment. As discussed previously, the functionality attributed to the network node 16 may be performed by a single processing or computing device, or may be performed by multiple such devices maintained by the service provider. The exemplary network node 16 illustrated in FIG. 9 may comprise a workstation, a telecommunications switch, or the like. The network node 16 includes a processor 100, a system memory 102, and a system bus 104. The system bus 104 provides an interface for system components including, but not limited to, the system memory 102 and the processor 100. The processor 100 can be any of various commercially available or proprietary processors. Dual microprocessors and other multi-processor architectures may also be employed as the processor 100.

The system bus 104 may be any of several types of bus structures that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and/or a local bus using any of a variety of commercially available bus architectures. The system memory 102 may include non-volatile memory 106 (e.g., read only memory (ROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), etc.), and/or volatile memory 108 (e.g., random access memory (RAM)). A basic input/output system (BIOS) 110 may be stored in the non-volatile memory 106, and can include the basic routines that help to transfer information between elements within the network node 16. The volatile memory 108 may also include a high-speed RAM such as static RAM for caching data.

The network node 16 may further include the computer-readable storage 112, which may comprise, for example, an internal hard disk drive (HDD) (e.g., enhanced integrated drive electronics (EIDE) or serial advanced technology attachment (SATA)) HDD (e.g., EIDE or SATA) for storage, flash memory, or the like. The storage 112 may store, for example, the configuration data 50, data usage quantifiers, and the like. The drives and associated computer-readable and computer-usable media provide non-volatile storage of data, data structures, computer-executable instructions, and so forth. Although the description of computer-readable media above refers to an HDD, it should be appreciated by those skilled in the art that other types of media which are readable by a computer, such as Zip disks, magnetic cassettes, flash memory cards, cartridges, and the like, may also be used in the exemplary operating environment, and further, that any such media may contain computer-executable instructions for performing novel methods of the disclosed architecture.

A number of program modules can be stored in the storage 112 and in the volatile memory 108, including an operating system 114 and one or more program modules 116, which may implement the functionality described herein in whole or in part, including, for example, functionality associated with the remote configuration module 44, the authentication module 48, the billing module 56, the rate limiting, policing, and prioritization module 52, and other processing and functionality described herein. It is to be appreciated that the embodiments can be implemented with various commercially available operating systems 114 or combinations of operating systems 114.

All or a portion of the embodiments may be implemented as a computer program product stored on a transitory or non-transitory computer-usable or computer-readable medium, such as the storage 112, which includes complex programming instructions, such as complex computer-readable program code, configured to cause the processor 100 to carry out the steps described herein. Thus, the computer-readable program code can comprise software instructions for implementing the functionality of the embodiments described herein when executed on the processor 100. The processor 100, in conjunction with the program modules 116 in the volatile memory 108, may serve as a control system for the network node 16 that is configured to, or adapted to, implement the functionality described herein.

An administrator may be able to enter commands and information into the network node 16 through one or more input devices, such as, for example, a keyboard (not illustrated); a pointing device, such as a mouse (not illustrated); or a touch-sensitive surface. Other input devices may include a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, or the like. These and other input devices may be connected to the processor 100 through an input device interface 118 that is coupled to the system bus 104, but can be connected by other interfaces such as a parallel port, an IEEE 1394 serial port, a Universal Serial Bus (USB) port, an IR interface, etc.

The network node 16 may also include one or more communication interfaces 120 for communicating with, for example, various networks, including the cellular network 14 and the WLAN network 20 discussed herein. The one or more communication interfaces 120 may comprise, for example, wired or wireless network interfaces. The network node 16 may also include a video port 122 that interfaces with a display 124 that provides information to the administrator.

FIG. 10 is a block diagram of the MHD 22 according to one embodiment. The exemplary MHD 22 illustrated in FIG. 10 may comprise any portable, mobile computing or processing device capable of establishing a wireless communications link, such as a smart phone like an Apple® iPhone®, an Android®-based phone, or the like, a laptop computer that includes cellular data interface circuitry, a computer tablet like the Apple® iPad®, Samsung Galaxy®, or the like, or a special purpose hotspot device, such as the Sprint® Overdrive® or the like. The MHD 22 includes a processor 130, a system memory 132, and a system bus 134. The system bus 134 provides an interface for system components including, but not limited to, the system memory 132 and the processor 130. The processor 130 can be any of various commercially available or proprietary processors. Dual microprocessors and other multi-processor architectures may also be employed as the processor 130.

The system bus 134 may be any of several types of bus structures that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and/or a local bus using any of a variety of commercially available bus architectures. The system memory 132 may include non-volatile memory 136 (e.g., read only memory (ROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), etc.) and/or volatile memory 138 (e.g., random access memory (RAM)). A basic input/output system (BIOS) 140 may be stored in the non-volatile memory 136, and can include the basic routines that help to transfer information between elements within the MHD 22. The volatile memory 138 may also include a high-speed RAM such as static RAM for caching data.

The MHD 22 may further include the computer-readable storage 142, which may comprise, for example, an internal hard disk drive (HDD) (e.g., enhanced integrated drive electronics (EIDE) or serial advanced technology attachment (SATA)) HDD (e.g., EIDE or SATA) for storage, flash memory, or the like. The storage 142 may store, for example, the configuration data 62, network configuration data 58, 60, and the like. The drives and associated computer-readable and computer-usable media provide non-volatile storage of data, data structures, computer-executable instructions, and so forth. Although the description of computer-readable media above refers to an HDD, it should be appreciated by those skilled in the art that other types of media which are readable by a computer, such as Zip disks, magnetic cassettes, flash memory cards, cartridges, and the like, may also be used in the exemplary operating environment, and further, that any such media may contain computer-executable instructions for performing novel methods of the disclosed architecture.

A number of program modules can be stored in the storage 142 and in the volatile memory 138, including an operating system 144 and one or more program modules 146, which may implement the functionality described herein in whole or in part, including, for example, functionality associated with the configuration module 46, the wireless router module 32, and other processing and functionality described herein. It is to be appreciated that the embodiments can be implemented with various commercially available operating systems 144 or combinations of operating systems 144.

All or a portion of the embodiments may be implemented as a computer program product stored on a transitory or non-transitory computer-usable or computer-readable medium, such as the storage 142, which includes complex programming instructions, such as complex computer-readable program code, configured to cause the processor 130 to carry out the steps described herein. Thus, the computer-readable program code can comprise software instructions for implementing the functionality of the embodiments described herein when executed on the processor 130. The processor 130, in conjunction with the program modules 146 in the volatile memory 138, may serve as a control system for the MHD 22 that is configured to, or adapted to, implement the functionality described herein.

A user, such as the owner 40, may be able to enter commands and information into the MHD 22 through one or more input devices, such as, for example, a keyboard (not illustrated); a pointing device, such as a mouse (not illustrated); or a touch-sensitive surface. Other input devices may include a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, or the like. These and other input devices may be connected to the processor 130 through an input device interface 148 that is coupled to the system bus 134, but can be connected by other interfaces such as a parallel port, an IEEE 1394 serial port, a Universal Serial Bus (USB) port, an IR interface, etc.

The MHD 22 may also include the wireless cellular interface 24 suitable for establishing a wireless communications link 26 with a cellular network, such as the cellular network 14. The MHD 22 may include the WLAN interface 28 suitable for establishing a wireless communications link 68 with a WLAN network, such as the WLAN network 20. The MHD 22 may include one or more other wireless interfaces 30 suitable for establishing other wireless communications links, such as ZigBee wireless communications links and Bluetooth® wireless communications links. The MHD 22 may also include video circuitry 150 that interfaces with a display 152 that provides information to the owner 40.

Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow. 

What is claimed is:
 1. A method for providing access to a service provider network associated with a service provider and comprising at least one network node, comprising: establishing, by the at least one network node, a first wireless communication link with a mobile hotspot device, the mobile hotspot device configured to establish a second wireless communication link with at least one client device; receiving, by the network node, an access request message from the mobile hotspot device, the access request message comprising credentials provided by the at least one client device; determining, by the network node, that the at least one client device is authorized to access the service provider network through the mobile hotspot device based on the credentials; and indicating to the mobile hotspot device that the at least one client device is authorized to access the service provider network through the mobile hotspot device.
 2. The method of claim 1, wherein the mobile hotspot device comprises a cellular phone of a subscriber of the service provider.
 3. The method of claim 1, further comprising: providing voice signals destined for the mobile hotspot device to the mobile hotspot device via the first wireless communication link while concurrently providing data destined for the at least one client device to the mobile hotspot device via the first wireless data communication link.
 4. The method of claim 1, further comprising: provisioning, by the network node, the mobile hotspot device with a wireless network having a predetermined SSID; and wherein the at least one client device seeks access to the mobile hotspot device in response to detecting the predetermined SSID.
 5. The method of claim 1, further comprising: providing a first quantity of data to the mobile hotspot device destined for a device other than the at least one client device; providing a second quantity of data to the mobile hotspot device destined for the at least one client device; maintaining a first data usage quantifier that tracks a first cumulative quantity of data provided to the device other than the at least one client device pursuant to a subscription associated with the mobile hotspot device; maintaining a second data usage quantifier that tracks a second cumulative quantity of data provided to the at least one client device pursuant to a subscription associated with the at least one client device; increasing the first data usage quantifier based on the first quantity of data but not based on the second quantity of data; and increasing the second data usage quantifier based on the second quantity of data.
 6. The method of claim 5, wherein the device other than the at least one client device comprises the mobile hotspot device.
 7. The method of claim 5, wherein the device other than the at least one client device comprises a second client device, the second client device being associated with the subscription associated with the mobile hotspot device.
 8. The method of claim 5, further comprising: making a determination that the second data usage quantifier exceeds a predetermined threshold; and based on the determination, de-authorizing access to the service provider network by the at least one client device.
 9. The method of claim 1, further comprising: receiving a first request for first data destined for the at least one client device; prior to delivering the first data receiving a second request for second data destined for the mobile hotspot device; prioritizing the second request over the first request based on a destination of the second data; and delivering the second data to the mobile hotspot device prior to delivering the first data to the at least one client device.
 10. The method of claim 1, wherein determining, by the network node, that the at least one client device is authorized to access the service provider network through the mobile hotspot device based on the credentials comprises determining that the credentials identify a subscriber of the service provider.
 11. The method of claim 1, further comprising: providing a message to the hotspot device for presentation to a user of the hotspot device that the at least one client device has requested access to the service provider network through the mobile hotspot device.
 12. A mobile hotspot device, comprising: at least one wireless interface configured to establish first and second wireless communication links; a processor coupled to the at least one wireless interface and configured to: communicate with a service provider network via the first wireless communication link; communicate with a client device via the second wireless communication link; receive a request from the client device to access the service provider network; submit the request, including credentials associated with the client device, to the service provider network; and receive authorization from the service provider network that the client device is authorized to access the service provider network.
 13. The mobile hotspot device of claim 12, wherein the processor is further configured to: route a plurality of requests for data received from the client device to the service provider network; and route a plurality of responses to the requests for data to the client device.
 14. The mobile hotspot device of claim 12, wherein the processor is further configured to: prior to submitting the request to access the service provider network, access configuration data identifying permitted client devices; and determining that the client device is identified as a permitted client device.
 15. The mobile hotspot device of claim 12, wherein the at least one wireless interface comprises a first wireless interface and a second wireless interface, the first wireless interface comprising a cellular wireless interface and establishing the first wireless communication link, and the second wireless interface comprising a WLAN wireless interface and establishing the second wireless communication link.
 16. The mobile hotspot device of claim 12, wherein the at least one wireless interface comprises a first wireless interface and a second wireless interface, the first wireless interface comprising a cellular wireless interface and establishing the first wireless communication link, and the second wireless interface comprising one of a Bluetooth® wireless interface and a ZigBee wireless interface, and establishing the second wireless communication link.
 17. The mobile hotspot device of claim 12, wherein the at least one wireless interface comprises a first wireless interface and a second wireless interface, the first wireless interface comprising a cellular wireless interface and the second wireless interface comprising a WLAN wireless interface, the processor further configured to: detect that the service provider network is accessible via both the first wireless interface and the second wireless interface; and select one of the first wireless interface and the second wireless interface to establish the first wireless communication link based on at least one criterion.
 18. The mobile hotspot device of claim 17, wherein the at least one criterion comprises a bandwidth of the first wireless interface compared to a bandwidth of the second wireless interface.
 19. The mobile hotspot device of claim 12, wherein the processor is further configured to: access a predetermined data usage threshold associated with the client device; make a determination that a quantity of data delivered to the client device via the mobile hotspot device has exceeded the predetermined data usage threshold; and in response to the determination de-authorize access to the service provider network by the client device.
 20. The mobile hotspot device of claim 12, wherein the processor is further configured to: receive a first request for first data from the at least one client device; receive a second request for second data from a user of the mobile hotspot device; and prioritize servicing the second request over the first request. 